Skip to content

Conversation

@MichaelOrlov
Copy link
Contributor

@MichaelOrlov MichaelOrlov commented Nov 13, 2025

Description

This PR makes topics persistent between writer's close() and open() API calls.

Reasoning:
Will be useful when creating topics via direct rosbag2_transport API or when calling Writer::close() and Writer::open() multiple times.

Is this user-facing behavior change?

Yes.

  • Topics will persist between the writer's close() and open() API calls.
  • The Writer::create_topic(..) and Writer::remove_topic(..) will not throw exceptions if the writer is not open.

Did you use Generative AI?

Yes. I used GitHub Copilot, GPT-4.o to help with writing unit tests and Doxygen comments.

Additional Information

No API/ABI changes. This PR can be backported.

Reasoning:
 Can be useful when creating topics via direct rosbag2_transport API or
 initiating close() and open() multiple times.
Signed-off-by: Michael Orlov <[email protected]>
@MichaelOrlov MichaelOrlov changed the title [Draft] Make topics persistent between writer's close() and open() API calls. Make topics persistent between writer's close() and open() API calls. Nov 13, 2025
@MichaelOrlov MichaelOrlov marked this pull request as ready for review November 13, 2025 23:02
@MichaelOrlov
Copy link
Contributor Author

This PR is ready for review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants